System and method for crowd-sourced environmental system control and maintenance

ABSTRACT

A system and method for crowd-sourced environmental system control and building maintenance includes a server for providing selective access to building occupants and managers. Users are permitted to generate building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module. The reports are each geo-located to locations within the building, and are then captured, stored, and aggregated at the server. The aggregated reports are sorted according to their geo-locations and comfort rules are used to (i) permit a manager at a client computer to access the server to respond, and/or (ii) automatically respond and assign a response status to particular reports. An inspection checklist interface is generated and populated to display a list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion, with the updated status of the reports being stored at the server.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/611,295, filed Jun. 1, 2017 (now issued as U.S. Pat. No. 10,422,542), which is a continuation of U.S. patent application Ser. No. 15/472,913, filed Mar. 29, 2017 (now issued as U.S. Pat. No. 10,215,435), which is a continuation of U.S. patent application Ser. No. 14/328,492, filed Jul. 10, 2014 (now issued as U.S. Pat. No. 9,625,922), which claims the benefit of and priority to U.S. Provisional Patent Application No. 61/844,494, filed on Jul. 10, 2013, and U.S. Provisional Patent Application No. 61/903,123, filed on Nov. 12, 2013, the contents of each of which are incorporated herein by reference in their entireties for all purposes.

TECHNICAL FIELD

This invention relates to web-enabled transactions for building system control, and more particularly to an automated system for crowd-sourced report generation, aggregation, and response for building systems.

BACKGROUND INFORMATION

Residential and commercial building occupants are often frustrated by comfort challenges, but feel powerless. At the same time, discomfort triggers—space is too hot, or too cold, or too drafty, can often signal poor HVAC design, operation, maintenance, or the need for other cost effective energy efficiency improvements. For many larger commercial buildings occupant discomfort related to temperature or other air quality issues, is a sign of an inefficient or poorly commissioned or ventilated building, or unresponsive/improperly designed or maintained HVAC controls. These conditions often lead to overheating or overcooling, causing occupants discomfort or in some cases, breathing difficulties.

A need exists for an efficient system and method capable of capturing, analyzing, and aggregating comfort and maintenance information from building occupants to produce actionable feedback to building personnel.

SUMMARY

In one aspect of the invention, a computer implemented system in a client-server environment, for crowd-sourced environmental system control and maintenance at a particular building, includes a computer server having a processor configured to process a series of modules. One of the modules is a login module configured to provide selective access to users via one or more client computers communicably coupled to the server, the users including (i) occupants of the building having first level permissions and (ii) managers having second level permissions, wherein said selective access is granted based on said permissions. A report access module actuatable by the users after having gained access to the server, is configured to generate a report interface displayable on the client computers to enable the users to generate one or more building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module. A geo-location module is configured to assign a location within the building to each building report. An aggregation module is configured to capture, store, and aggregate the building reports at the server. A View/Sort module is configured to sort the aggregated reports according to their assigned locations, and to transmit the sorted reports to the one or more client computers for display. A rule storage module is configured to store a set of comfort rules for the building, while a Response/Notification module is configured to (i) permit a manager at a client computer to access the server to select for response, and assign a response status, to particular reports, and/or (ii) automatically respond and assign a response status to particular reports in accordance with said set of comfort rules. A checklist storage module is configured to store a list of preventative maintenance items for the building. An inspection module is configured to generate and populate a checklist interface on the user device, the checklist interface configured to display the list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion of each individual task. The aggregation module is further configured to store the status of the reports.

Another aspect of the invention is a computer implemented method in a client-server environment, for crowd-sourced environmental system control and maintenance at a particular building. The method includes using a computer server having a processor to perform a series of operations, including actuating a login module to provide selective access to users via one or more client computers communicably coupled to the server, the users including (i) occupants of the building having first level permissions and (ii) managers having second level permissions, wherein said selective access is granted based on said permissions. Additional operations include enabling users after having gained access to the server, to actuate a report access module to generate a report interface displayable on the client computers to enable the users to generate one or more building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module. A geo-location module is actuated to assign a location within the building to each building report. An aggregation module is actuated to receive the building reports from the client computers, and to store and aggregate the building reports at the server. The method further includes actuating a View/Sort module to sort the aggregated reports according to their assigned locations, and to transmit the sorted reports to the one or more client computers for display, and actuating a rule storage module to store a set of comfort rules for the building. A Response/Notification module is actuated to (i) permit a manager at a client computer to access the server to select for response, and assign a response status, to particular reports, and/or (ii) automatically respond and assign a response status to particular reports in accordance with said set of comfort rules. A checklist storage module is actuated to store a list of preventative maintenance items for the building, and an inspection module is actuated to generate and populate a checklist interface on the user device, the checklist interface being configured to display the list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion of each individual task. The aggregation module is then used to store the status of the reports.

In still another aspect of the invention, an article of manufacture for crowd-sourced environmental system control and maintenance at a particular building, in a client-server environment, includes a computer usable medium having a computer readable program code embodied therein, for performing a series of operations, including actuating a login module to provide selective access to users via one or more client computers communicably coupled to the server, the users including (i) occupants of the building having first level permissions and (ii) managers having second level permissions, wherein said selective access is granted based on said permissions. Additional operations include enabling users after having gained access to the server, to actuate a report access module to generate a report interface displayable on the client computers to enable the users to generate one or more building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module. A geo-location module is actuated to assign a location within the building to each building report. An aggregation module is actuated to receive the building reports from the client computers, and to store and aggregate the building reports at the server. The method further includes actuating a View/Sort module to sort the aggregated reports according to their assigned locations, and to transmit the sorted reports to the one or more client computers for display, and actuating a rule storage module to store a set of comfort rules for the building. A Response/Notification module is actuated to (i) permit a manager at a client computer to access the server to select for response, and assign a response status, to particular reports, and/or (ii) automatically respond and assign a response status to particular reports in accordance with said set of comfort rules. A checklist storage module is actuated to store a list of preventative maintenance items for the building, and an inspection module is actuated to generate and populate a checklist interface on the user device, the checklist interface being configured to display the list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion of each individual task. The aggregation module is then used to store the status of the reports.

The features and advantages described herein are not all-inclusive and, in particular, many additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specification, and claims. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and not to limit the scope of the inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1A is a schematic representation of aspects of an embodiment of the present invention;

FIG. 1B is a schematic representation of aspects of an embodiment of the present invention;

FIG. 1C is a block diagram of one embodiment of a network-based transaction facility according to an embodiment of the present invention;

FIG. 2 is a block diagram of one embodiment of a database maintained by a database engine server;

FIG. 3 is a diagrammatic representation of one embodiment of a user table within the database;

FIG. 4A is a diagrammatic representation of one embodiment of a property information table within the database;

FIG. 4B is a schematic representation of a floor plan usable with embodiments of the present invention;

FIG. 4C is a table with summaries of information shown in the floor plan of FIG. 4B;

FIG. 4D is a table populated with data and rules in accordance with embodiments of the present invention;

FIG. 5 is a simplified schematic diagram of one embodiment of a system within which aspects of the present invention may be embodied;

FIG. 6 is a block diagram of one embodiment of an interface sequence in accordance with embodiments of the present invention;

FIG. 7A is a flow chart of one embodiment for a method of the present invention;

FIG. 7B is a flow chart of another embodiment for a method of the present invention;

FIG. 7C is a flow chart of another embodiment for a method of the present invention;

FIG. 8 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 9 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 10 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 11 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 12 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 13 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 14 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 15 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6; FIG. 8 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 16A is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 16B is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 16C is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 17 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6;

FIG. 18 is an exemplary representation of an interface included in the sequence of interfaces shown in FIG. 6; and

FIG. 19 is a block diagram of one embodiment of a computer system usable in various aspects of the present invention.

DETAILED DESCRIPTION

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized. It is also to be understood that structural, procedural and system changes may be made without departing from the spirit and scope of the present invention. In addition, well-known structures, circuits and techniques have not been shown in detail in order not to obscure the understanding of this description. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.

As used in the specification and in the appended claims, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly indicates otherwise. For example, reference to “a facility” includes a plurality of such facility. In another example, reference to “an analysis” includes a plurality of such analyses.

Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. All terms, including technical and scientific terms, as used herein, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs unless a term has been otherwise defined. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning as commonly understood by a person having ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure. Such commonly used terms will not be interpreted in an idealized or overly formal sense unless the disclosure herein expressly so defines otherwise.

General Overview

A method and apparatus for providing automated report generation, aggregation, and response, in a network-based transaction facility are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details.

Referring to FIG. 1A, embodiments of the present invention offer building owners, operators, and occupants a new and powerful way to share information about comfort, maintenance, and safety issues with an easy to use smart device application. These embodiments convert this crowd sourced feedback into time stamped, geo-located aggregated reports/maps, which are actionable through a custom portal allowing building owners or facility managers to respond more rapidly and cost effectively to occupant concerns. These embodiments democratize and amplify the voices of building occupants, while helping building owners to pinpoint energy and operational saving opportunities. Referring to FIG. 1A, users may open application 70, identify a location 72, e.g., by scanning a QR Code, and generate a maintenance report 74, an inspection report 76 and/or a comfort report 78.

Referring now to FIG. 1B, once these reports are collected at 80, they are aggregated and analyzed (e.g., mapped) based on location at 82, and then automatically communicated to an appropriate recipient for response 84. In these embodiments, thermal comfort is facilitated by leveraging the power of employees to identify energy savings opportunities, improve comfort and worker productivity. Facilities management is facilitated by collecting, aggregating, and delivering real-time, geo-located reports on comfort and maintenance issues. Environmental compliance and inspection is facilitated by replacing the clipboard with real-time, site-specific environmental compliance reporting.

Various embodiments operate by initially having facility managers identify locations for data collection in and/or around particular properties. Markers are printed, delivered, and placed at the identified locations. Employees/Inspectors are notified, asked to download the application, and begin reporting. Facilities managers gain instant access to the secure portal where the data is aggregated and displayed. From the inventive platform, maintenance reports are converted into work orders that can be efficiently organized, addressed, and stored. As these reports are processed the employees who filed them are notified of progress through their phones. In particular embodiments, building systems are adjusted automatically in response to the aggregated, geo-located reports.

Potential benefits include: engaging employees and making them part of the solution; improving health, safety and security within an organization; collection of meaningful data that can be leveraged to support high-impact recommendations; use of predictive analytics to identify maintenance needs before they become problems; and/or optimization of workflow efficiency for building maintenance.

Reporting comfort and/or maintenance issues is simply the first step. By capturing and highlighting occupant discomfort, occupants can provide a compelling feedback loop to building owners—and the cloud—to address these problems and reduce energy consumption, while improving building occupants' comfort. Initial embodiments may simply provide crowd sourced feedback to building facility managers/owners informing them the extent to which building HVAC system design, set points, and overall operation is meeting occupant comfort expectations. Ultimately, crowd sourced reactions would directly influence or directly control HVAC operation (temperature and humidity levels) alongside required ventilation/air exchange rates (e.g. ASHRAE standards 62.1 and 90.1) to better match the comfort needs of a preponderance of building occupants by tying feedback directly to the building's energy management system. For example, if 90% of the occupants in a convention center feel too chilly, air conditioning set points may be raised slightly and energy consumption reduced.

Particular embodiments capture crowd sourced comfort level information periodically via a simple icon based interface. Occupants may receive a simple periodic query—perhaps via text message, via Twitter, or other platforms—asking them to characterize their comfort level (e.g. very cold, somewhat cold, comfortable, warm, very warm). Users may then respond using the system interface shown and described herein. Taken together, this data would inform building facility managers, and directly influence building HVAC set points. Looking beyond the building boundary, in various embodiments, this aggregated data may be shared on-line in a Google maps-type interface where users could mouse over buildings and see reports in the aggregate (e.g. how many, and when, users reported being uncomfortable). These reports would be updated over time based on user feedback. Such user feedback would motivate building owners to react, due to the potential positive or negative occupant ratings that could have a real effect on the property's value. At the same time, building owners could voluntarily report improvement they had made to their buildings at the same web based platform. These embodiments would thus actively support building owners who take proactive steps to provide the most comfortable and energy efficient buildings.

Application deployment/partnership options may include: Event registration sites; Employer databases/corporate sustainability leadership; Hotels; Public Transit/trains, etc. Additional applications may include power supply impacts—facility owners, utilities, and grid operators could use this platform to communicate important grid and air quality data to building occupants. For example, a preponderance of building occupants might be willing to tolerate a slightly higher indoor temperature during a hot summer day if they knew that by shedding that load, grid operators could avoid starting coal fired peaking power plants. In other words, these embodiments may complement and augment existing demand response programs.

Also, by use of relatively high resolution location data, e.g., by use of QR Codes, microGPS, etc., facility operators may begin to better understand HVAC design and operation problems at the distribution level, targeting solutions such as more localized controls, VAV (Variable Air Volume) box operation, or other conditions (e.g. excessive passive solar) addressing tenant comfort concerns and related energy use.

Building owners and users could capture more value from the app over time by pushing more and more sophisticated questions to app users, particularly repeat users, including questions like: “how would you rate the air quality in your building?” Occupants who participate in using these embodiments will be providing valuable data on the building systems, but will also be educating building managers about their preferences. This understanding will allow building owners and employers to place workers in environments with similar temperature preferences to potentially improve work satisfaction and productivity. Repeat users may build a profile and climate preference.

Terminology

For the purposes of the present specification, the term “transaction” shall be taken to include any communications between two or more entities and shall be construed to include, but not be limited to, transferring data including reports and responses between computers, downloading software applications or “apps” including graphical user interface components, and commercial transactions including sale and purchase transactions, and the like.

As used herein, the terms “computer” and “end-user device” are meant to encompass a workstation, personal computer, personal digital assistant (PDA) or smart phone, wireless telephone, tablet, or any other suitable computing device including a processor, a computer readable medium upon which computer readable program code (including instructions and/or data) may be disposed, and a user interface. Terms such as “server”, “application”, “engine” and the like are intended to refer to a computer-related component, including hardware, software, and/or software in execution. For example, an engine may be, but is not limited to being, a process running on a processor, a processor including an object, an executable, a thread of execution, a program, and a computer. Moreover, the various components may be localized on one computer and/or distributed between two or more computers. The terms “real-time” and “on-demand” refer to sensing and responding to external events nearly simultaneously (e.g., within milliseconds or microseconds) with their occurrence, or without intentional delay, given the processing limitations of the system and the time required to accurately respond to the inputs.

Terms such as “component,” “module”, “control components/devices,” “messenger component or service,” and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer. By way of illustration, both an application running on a server and the server (or control related devices) can be components. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers or control devices.

Programming Languages

The system and method embodying the present invention can be programmed in any suitable language and technology, such as, but not limited to: C++; Visual Basic; Java; VBScript; Jscript; BCMAscript; DHTM1; XML and CGI. Alternative versions may be developed using other programming languages including, Hypertext Markup Language (HTML), Active ServerPages (ASP) and Javascript. Any suitable database technology can be employed, such as, but not limited to, Microsoft SQL Server or IBM AS 400.

Referring now to the figures, embodiments of the present invention will be more thoroughly described.

Transaction Facility

FIG. 1 is a block diagram illustrating an exemplary network-based transaction facility in the form of an Internet-based report generation and aggregation facility 10. The report facility 10 includes one or more of a number of types of front-end servers, namely page servers 12 that deliver web pages (e.g., markup language reports), picture servers 14 that dynamically deliver images to be displayed within Web pages, CGI (Common Gateway Interface) servers 18 that provide an intelligent interface to the back-end of facility 10, and search servers 20 that handle search requests to the facility 10. E-mail/communication servers 21 provide, inter alia, automated e-mail (and optionally, text and/or social media) communications to users of the facility 10. The back-end servers may include a database engine server 22, a search index server 24 and a payment (e.g., credit card and/or subscription) database server 26, each of which may maintain and facilitate access to a respective database. Facility 10 may also include an administrative application server 28 configured to provide various administrative functions.

The network-based report generation and aggregation facility 10 may be accessed by a client program 30, such as a browser (e.g., the Internet Explorer distributed by Microsoft) that executes on a client machine 32 such as a smart phone, and accesses the facility 10 via a network such as, for example, the Internet 34. Other examples of networks that a client may utilize to access the facility 10 include a wide area network (WAN), a local area network (LAN), a wireless network (e.g., a cellular network), or the Plain Old Telephone Service (POTS) network.

Database Structure

FIG. 2 is a database diagram illustrating an exemplary database 23, maintained by and accessed via the database engine server 22, which at least partially implements and supports the report generation and aggregation facility 10. The database 23 may, in one embodiment, be implemented as a relational database, and includes a number of tables having entries, or records, that are linked by indices and keys. In an alternative embodiment, the database 23 may be implemented as collection of objects in an object-oriented database.

As shown, central to the database 23 is a user table 40, which contains a record for each user of the facility 10. The database 23 also includes tables 42 that may be linked to the user table 40. Specifically, the tables 42 may include property report (e.g., geo-located building report) table 44, and various property specific tables, such as a building locations table 45, inspection list table 46, comfort rules table 50, and a user-customizable table 52. A user record in the user table 40 may be linked to multiple reports that are being, or have been, generated via the facility 10 and for which records exist within the report tables 42. The database 23 may also include a comment table 48 populatable with comment records that may be linked to one or more report records within the report tables 42. A number of other tables may also be linked to the user table 40, such as an accounts table 56, an account balances table 58 and a transaction record table 60.

FIG. 3 is a diagrammatic representation of an exemplary embodiment of the user table 40 that is populated with records, or entries, for each user of the facility 10. As shown, table 40 includes a user identifier column 61 that stores a unique identifier for each user. A name column 63 may store a first name, a middle initial and a last name for each user. An address column 65 may store address information and/or other contact information for each user, e.g. an employer name, and/or street name and number, city, zip code, state, email address, etc. A phone number column 67 stores a phone (e.g., mobile) number for each user. A permission status column 69 may store, for each user, a value identifying the user's permission status, i.e., the user's ability to access particular features of the system, such as those typically provided to a manager or other user tasked with responding to particular reports, etc. It should be recognized that the amount of information stored may vary depending on the permission level assigned to the particular user. Table 40 may also store any additional information that may be desired for particular applications. For example, subscription information may be recorded (not shown), in which different values may be assigned to indicate whether a user has a currently valid subscription, has an expired subscription (which may provide only limited access to facility 10). It will be appreciated that any information other than that described above may populate the user table 40 without loss of generality.

FIG. 4A is a diagrammatic representation of an exemplary embodiment of a table 44 populated with property report records generated during use of the report generation facility 10. As shown, table 44 includes a property ID column 60 to identify particular properties, a location ID/QR column 62 to track particular locations, e.g., as designated with a QR Code or similar tag placed at the location, a property rules column 64 to provide a pointer or other reference to maintenance lists 45, inspection lists 46, comfort rules tables 50, and/or user-customizable table 52, associated with the particular property. A room type column 66 provides the type of space tagged by the QR Code, e.g., conference room, private office, etc. Report content column 68 is populated with the actual content of a report generated by the system, along with the User ID of the individual responsible for generating the report.

It will be appreciated that in particular embodiments, other descriptive information may also populate table 44, without departing from the scope of the present invention. For example, additional columns may be provided to capture information regarding the number of employees typically occupying a particular room type, and/or the number of rooms of a particular room type in the property or HVAC zone. Yet another column, for example, may identify the HVAC zone within which a particular location ID/QR Code is located.

Turning now to FIGS. 4B and 4C, information used to populate table 44 may be obtained from a floor plan 85 (FIG. 4B) of a particular property, which as shown, has been segregated into various room types, such as large workspaces 86, common areas 87, individual offices 88, and conference rooms 89. In FIG. 4C, some of the room types have optionally been associated with additional information, such as typical occupancy levels (for Large Workspaces), and the number of rooms of a particular type, e.g., Individual Offices and Conference Rooms.

Report Generation and Aggregation Process

As mentioned hereinabove, embodiments of the present invention provide geo-located mobile application that allows employees and managers to report comfort levels and maintenance issues from anywhere, easily and instantaneously. This information is processed through a cloud-based report aggregation server(s) and shared with managers in real-time through a secure portal that provides comfort and maintenance information, optionally including preventive maintenance such as inspection lists, in aggregated reports. This data can be used to engage employees, improve workflow, drive operational savings, and optimize organizational performance.

These embodiments enable such report generation and aggregation in a real-time, web-based, client-server environment. While the present invention is discussed within the environment of the exemplary report aggregation facility 10, it will readily be appreciated that the present invention may be used in any number of environments including network and on-line based transaction facilities in business-to-business, business-to-consumer and consumer-to-consumer applications.

FIG. 5 is a simplified block diagram of a system 90 for generating reports in accordance with an exemplary embodiment of the present invention. In this embodiment, a client computer 92 is coupled to a transaction computer 98 via a communications network (e.g. a wide area network) 94. The client computer 92 represents a device that allows a user to interact with the report generation and aggregation facility 10 or any other transaction facility 98. In one embodiment, the client computer 92 presents to the user a report generation interface for generating reports and viewing content aggregated be the transaction computer 98.

The transaction computer 98, which supports a facility such as shown at 10 of FIG. 1C, handles transactions between various participants of the facility 10 including the user of the client computer 92. In one embodiment, the transaction computer 98 may initially receive the personal information of the participant from the client computer 92, and generate a subscription result which determines whether, and to what extent, the user is granted access to the facility 10. The transaction computer then facilitates the aggregation of reports in accordance with various user interfaces presented by the computer 98, via the client computer 92, to the user.

FIG. 6 shows a series 100 of interfaces/modules, such as may take the form of a series of objects (or methods), that may be implemented by the report aggregation facility 10, e.g., in combination with the various tables of database 23, for the purposes of generating and aggregating reports. The series 100 of interface modules shown in FIG. 6 will be described with reference to exemplary representations of the various interfaces as shown in FIGS. 8-18. It should be noted that the various modules may reside and operate on the facility 10 or alternatively, one or more of the modules, or components thereof, may be initially downloaded from the facility 10, e.g., as an application or “app”, for installation on a user's smart phone, tablet or other user device 32. The skilled artisan will recognize that distribution of some components onto user devices may provide benefits such as reducing the amount of communication traffic between the user devices and the facility 10.

As shown, series 100 includes a login module 102, configured to generate a login interface through which a user of the facility 10 provides at least a user identifier and associated password. The login module may include a permissions module configured to provide selective access to the server by one or more users in accordance with permissions assigned to each user, e.g., based on whether the user is an employee of a building tenant or other building occupant, or whether the user is a manager or other responsible party having authority to address reports aggregated by the facility 10. Optionally, some users, such as the aforementioned manager, may also be requested to pay a subscription fee for access to the system.

A report access module 104 is configured to generate a report interface, such as shown at 200 in FIG. 8. Module 104 interacts with the various tables of database 23 (FIG. 1C) to enable a user to generate a new report by scanning a QR code at 202 (FIG. 9), using geo-location module 106, or by looking up a particular location, e.g., within a particular building at 204 (FIG. 10), which then permits the user to select the type of report at 206 (FIG. 11). Selecting “Rate Thermal Comfort” actuates thermal module 108, while selecting “Report a Maintenance Issue” actuates maintenance module 110, both of which permit the user to supply data, such as a thermal rating at 208 of FIG. 12 and/or a maintenance request at 210 of FIG. 13. An optional time-stamp module 126 is configured to store a time stamp denoting the time of creation and/or storage at the server, of each building report.

The reports are uploaded from the user devices 32 to the facility 10 (FIG. 1C) where aggregation module 112 aggregates and stores them in database 23 (FIG. 2). An optional Comment/Customize module 114 permits a user to add custom text or images to the report, such as at 210 of FIG. 13, and/or to comment on others' reports, such as by selecting the ‘agree’ icon to support others' reports as shown at 212 of FIG. 14. Rule Storage module 116 enables rules to be uploaded for storage in tables 45, 46, 50 and/or 52 (FIG. 2), and/or accessed during responses as discussed hereinbelow. View/Sort module 118 actuates the interfaces 212 and 214 of FIGS. 14 and 15 to display aggregated reports from one or more users. Response/Notification module 120 actuates interfaces 216, 218 and 220 of FIGS. 16A-16C, which permit the user, which in this instance is a responsible party such as a manager having relatively high level permissions, to access the system to select specific reports to see detail and manage reports. Examples include adding a detailed comment (FIG. 16A), entering or changing status of a report, e.g., ‘resolved’ (FIG. 16B), which may include automatically notifying the user who originally submitted the report, and/or assigning the report to another user (colleague) for appropriate action (FIG. 16C), which may also include automatically notifying the assignee. It is noted that the notifications provided by module 120 may be accomplished automatically in any convenient manner, such as via email, text, etc., or via in-app notification, using email/communication server 21 (FIG. 1C). An example of an in-app notification is shown in FIG. 17, in which an ‘assigned to me’ interface 222 may display all reports that have been assigned to a particular user for resolution.

In addition to automatic notifications, response module 120 may also provide other automatic responses. For example, module 120 may automatically adjust building controls (e.g., HVAC controls) in accordance with the predetermined rules, e.g., comfort rule table 50, for the particular property, which may be accessed by rule storage module 116. One example of a rule table 50 is shown in FIG. 4D. In this example, system 10 has received and aggregated temperature reports from 30 out of 38 users located in a particular HVAC zone. As also shown, 20 of the users are requesting a temperature increase, while 5 are requesting a decrease, and 5 are requesting no temperature change. The rule table includes a weighting rule, which in this example, is pro rata, with 50 percent of the neutral ‘no change’ weightings being subtracted from each of the ‘increase’ and ‘decrease’ weights. An increase/decrease weighting rule subtracts the ‘decrease’ weighting from the ‘increase’ weighting, to yield a net weighting which if positive, corresponds to a percentage increase, and if negative corresponds to a percentage decrease of the ‘Max Change’ in temperature parameter. In the example shown, the aggregated reports produce a net weighting of +0.50 which dictates a positive adjustment of 50 percent of the ‘Max Change’ parameter of 5 degrees, to yield a recommended increase of 2.5 degrees. This recommended change may be effected automatically, by a transmission to the building HVAC system, or alternatively, may be sent to the interface 218 of FIG. 16B for action by a manager or other responsible party.

Response module 120 may also include an inspection module 122 configured to generate and populate a checklist display 224 such as shown in FIG. 18. The checklist interface enables a user to identify, e.g., with a checkmark, the particular asset being inspected. Aggregation module 124 serves to store and aggregate the various reports, including any comments/customization and responses, while also providing various reporting capabilities such as shown at 82 of FIG. 1B, and as will be discussed in greater detail hereinbelow.

Exemplary methods associated with system 100 of the present invention, will now be described as illustrated by the flow chart of FIGS. 7A and 7B.

Referring now to FIG. 7A, a method 700 for configuring the system for environmental comfort use at a particular property is shown and described. At 708, a list of rooms, including common areas, for the property is obtained, e.g., using floor plans such as shown in FIG. 4B, or created by touring the property and counting rooms, etc. At 710, a list of locations of interest within the rooms is generated. At 712, unique tags, such as individualized QR Codes, are generated for each location of interest. At 714, the tags are placed at the locations of interest, e.g., by printing the QR Codes onto markers which are physically placed at their corresponding locations. It should be noted that the locations of interest may be determined as granularly as desired. For example, a single room may have multiple tags, such as to capture comfort data at opposite ends of a large conference table. At 716, each location of interest is optionally mapped to an HVAC zone in the building. At 718, a set of rules (e.g., comfort, maintenance, inspection, etc.) rules is set for the particular property, e.g., to determine how often and how much the temperature can be changed by the system within an HVAC zone, etc. At 720, user contact information is captured and stored to table(s) 40, and notification, e.g., by email, text, social media, etc., is sent to employees or occupants of the property letting them know about the system and providing instruction on how to use it.

Referring now to FIG. 7B, a method 702 for operating system 100 is shown and described. As shown, the method 702 commences with enabling the login module at 730 to provide user interface information to a user of the transaction facility at client 32 (FIG. 1). More specifically, the user interface information may provide a login interface via login module 102 (FIG. 6). Subsequent to the login by the user, at 732 the report access module is actuated to generate a report interface displayable on the client computers to enable the users to generate one or more building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module. At 734, the geo-location module 106 is actuated to assign a location within the building to each building report. At 736, the aggregation module 112 is actuated to receive the building reports from the client computers, and to store and aggregate the building reports at the server. At 738, the View/Sort module 118 sorts the aggregated reports according to their assigned locations, and transmits the sorted reports to the one or more client computers for display. At 740, rule storage module 116 is actuated to store any comfort rules for the building that have not previously been loaded into database 23 (FIG. 1C). At 742, Response/Notification module 120 is actuated to (i) permit a manager at a client computer to access the server to select for response, and assign a response status, to particular reports, and/or (ii) automatically respond and assign a response status to particular reports in accordance with said set of comfort rules. At 744, checklist storage module 122 is actuated to store a list of preventative maintenance items for the building. At 746, inspection module 124 is actuated to generate and populate a checklist interface on the user device, the checklist interface configured to display the list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion of each individual task. At 748, the aggregation module 112 is actuated to store the status of the reports.

Various optional additions to method 702 are shown in flowchart 704 of FIG. 7C. As shown, at 750, report access module 104 is actuated to permit a client computer to generate a building report by scanning a QR code disposed at a predetermined location within the building. At 752, report access module 104 is actuated to permit a client computer to generate a building report by looking up a particular location within the building. At 754, report access module 104 is actuated to permit a client computer to apply a thermal comfort rating to one or more of the thermal reports. At 756, report access module 104 is actuated to permit a client computer to apply a maintenance request to one or more maintenance reports. At 758, optional time-stamp module 126 is actuated to store a time stamp denoting the time of creation and/or storage at the server, of each building report. At 760, optional Comment/Customize module 114 is actuated to permit a user at a client computer to add custom text and/or images to a report. At 762, step 760 further includes permitting the user to comment on reports. At 766, Response/Notification module 120 is actuated to automatically adjust the environmental control system in accordance with the predetermined rules for the building. At 768, Response/Notification module 120 is configured to aggregate and assign weights to reports associated with a particular location, and to use the weights to generate a control signal to adjust one or more operational parameters of the environmental control system. At 770, Response/Notification module 120 is actuated to permit a user, via the one or more client computers, to add a comment to one or more reports. At 772, step 770 further includes permitting a manager, via the one or more client computers, to assign one or more reports to one or more particular users for response.

It should be recognized that in the embodiments shown and described hereinabove, heat maps, such as shown at 82 in FIG. 1B, may be automatically generated and displayed in the user device interface(s) once thermal reports are aggregated. Moreover, as reports come in notifications may be provided directly to the individuals who need them. For example a comfort report may be delivered directly to the smart phone device of the person who manages the building management system, but a report on the generator may go to the device of an appropriate Environmental Health and Safety professional.

Particular embodiments may also be configured to accept an initiation of a temperature change by any individual who works in a particular zone. This process may be generally the same for every kind of occupied office space except the individual office on a single room zone. In that case, the occupant could increase the set-point on his or her own (within normal set-point ranges).

In addition to the rules in the temperature adjustment example shown and described hereinabove, the temperature change mechanism may have any number of additional rules, such as those that limit the number of changes that can be initiated by per day or per hour. Moreover, the rules may be space (zone) specific. The rules are typically set by the employer, or building manager and may be adjusted easily as needed.

Once a temperature change is initiated all of the employees in the zone may be notified by any convenient method. An exemplary notification may state:

“An individual in your zone is uncomfortable and has requested a temperature change. Your feedback is important so please let us know your preference to increase, decrease or maintain the current temperature. To do so please open the CrowdComfort application and provide your choice. In order for us to account for your temperature preference we will need your participation within 5 minutes of receipt of this notice.”

After the 5 minute period the votes may be tabulated by embodiments of the present invention.

It should also be recognized that data may be gathered an accumulated and a profile generated for each user submitting a comfort report. For individuals that are often uncomfortable, managers may begin to address their levels at an individual level as opposed to at the system/zone level. Moreover, users who are habitual outliers may be accorded less weight than other users. Still further, although QR Codes have been shown and described as a convenient geo-location device, other approaches for geo-location may include Wi-Fi, Bluetooth, I-Beacon, RFID or other location method to send the notification only to people within a particular zone.

It should also be recognized that although the various embodiments have been shown and described with respect to particular buildings, the embodiments need not be limited solely to interior applications. Rather, the embodiments may be applied to various property types, including buildings and campuses having both interior and exterior locations of interest, including rooftop decks and equipment, courtyards, patios, etc., for which it may be desirable to receive and aggregate comfort, maintenance, and/or inspection reports.

FIG. 19 shows a diagrammatic representation of a machine in the exemplary form of a computer system 300 within which a set of instructions, for causing the machine to perform any one of the methodologies discussed above, may be executed. In alternative embodiments, the machine may include a network router, a network switch, a network bridge, Personal Digital Assistant (PDA), a cellular telephone, a web appliance or any machine capable of executing a sequence of instructions that specify actions to be taken by that machine.

The computer system 300 includes a processor 302, a main memory 304 and a static memory 306, which communicate with each other via a bus 308. The computer system 300 may further include a video display unit 310 (e.g., a liquid crystal display (LCD), plasma, cathode ray tube (CRT), etc.). The computer system 300 may also include an alpha-numeric input device 312 (e.g., a keyboard or touchscreen), a cursor control device 314 (e.g., a mouse), a drive (e.g., disk, flash memory, etc.,) unit 316, a signal generation device 320 (e.g., a speaker) and a network interface device 322.

The drive unit 316 includes a computer-readable medium 324 on which is stored a set of instructions (i.e., software) 326 embodying any one, or all, of the methodologies described above. The software 326 is also shown to reside, completely or at least partially, within the main memory 304 and/or within the processor 302. The software 326 may further be transmitted or received via the network interface device 322. For the purposes of this specification, the term “computer-readable medium” shall be taken to include any medium that is capable of storing or encoding a sequence of instructions for execution by the computer and that cause the computer to perform any one of the methodologies of the present invention, and as further described hereinbelow.

Furthermore, embodiments of the present invention include a computer program code-based product, which includes a computer readable storage medium having program code stored therein which can be used to instruct a computer to perform any of the functions, methods and/or modules associated with the present invention. The non-transitory computer readable medium includes any of, but not limited to, the following: CD-ROM, DVD, magnetic tape, optical disc, hard drive, floppy disk, ferroelectric memory, flash memory, phase-change memory, ferromagnetic memory, optical storage, charge coupled devices, magnetic or optical cards, smart cards, EEPROM, EPROM, RAM, ROM, DRAM, SRAM, SDRAM, and/or any other appropriate static, dynamic, or volatile memory or data storage devices, but does not include a transitory signal per se.

The above systems are implemented in various computing environments. For example, the present invention may be implemented on a conventional IBM PC or equivalent, multi-nodal system (e.g., LAN) or networking system (e.g., Internet, WWW, wireless web). All programming and data related thereto are stored in computer memory, static or dynamic or non-volatile, and may be retrieved by the user in any of: conventional computer storage, display (e.g., CRT, flat panel LCD, plasma, etc.) and/or hardcopy (i.e., printed) formats. The programming of the present invention may be implemented by one skilled in the art of computer systems and/or software design.

In the preceding specification, the invention has been described with reference to specific exemplary embodiments for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.

It should be further understood that any of the features described with respect to one of the embodiments described herein may be similarly applied to any of the other embodiments described herein without departing from the scope of the present invention. 

Having thus described the invention, what is claimed is:
 1. A computer implemented system in a client-server environment, for crowd-sourced environmental system control and maintenance at a particular building, the system comprising a computer server having a processor configured to process: a login module configured to provide selective access to users via one or more client computers communicably coupled to the server, the users including (i) occupants of the building having first level permissions and (ii) managers having second level permissions, wherein said selective access is granted based on said permissions; a report access module actuatable by the users after having gained access to the server, the report access module configured to generate a report interface displayable on the client computers to enable the users to generate one or more building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module; a geo-location module configured to assign a location within the building to each building report based on a floor plan of the building; an aggregation module configured to capture, store, and aggregate the building reports at the server along with additional information related to the building reports obtained from the floor plan; a View/Sort module configured to sort the aggregated reports according to their assigned locations, and to transmit the sorted reports to the one or more client computers for display; a rule storage module configured to store a set of comfort rules for the building; a Response/Notification module configured to (i) permit a manager at a client computer to access the server to view building reports and additional information stored by the aggregation module and to select for response, and assign a response status to, particular reports, and/or (ii) automatically respond and assign a response status to particular reports in accordance with said set of comfort rules; a checklist storage module configured to store a list of preventative maintenance items for the building; an inspection module configured to generate and populate a checklist interface on the user device, the checklist interface configured to display the list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion of each individual task; and the aggregation module further configured to store the status of the reports.
 2. The system of claim 1, wherein the report access module is configured to permit a client computer to generate a building report by scanning a QR code disposed at a predetermined location within the building.
 3. The system of claim 1, wherein the report access module is configured to permit a client computer to generate a building report by looking up a particular location within the building.
 4. The system of claim 1, wherein the report access module is configured to permit a client computer to apply a thermal comfort rating to one or more of the thermal reports.
 5. The system of claim 1, wherein the report access module is configured to permit a client computer to apply a maintenance request to one or more maintenance reports.
 6. The system of claim 1, further comprising a time-stamp module configured to store a time stamp denoting the time of creation and/or storage at the server, of each building report.
 7. The system of claim 1, further comprising a Comment/Customize module configured to permit a user at a client computer to add custom text and/or images to a report.
 8. The system of claim 7, wherein the Comment/Customize module is further configured to permit the user to comment on reports.
 9. The system of claim 1, wherein the Response/Notification module is configured to automatically adjust the environmental control system in accordance with the predetermined rules for the building.
 10. The system of claim 9, wherein the Response/Notification module is configured to aggregate and assign weights to reports associated with a particular location, and to use the weights to generate a control signal to adjust one or more operational parameters of the environmental control system.
 11. The system of claim 1, wherein the Response/Notification module is further configured to permit a user, via the one or more client computers, to add a comment to one or more reports.
 12. The system of claim 11, wherein the Response/Notification module is further configured to permit a manager, via the one or more client computers, to assign one or more reports to one or more particular users for response.
 13. A computer implemented method in a client-server environment, for crowd-sourced environmental system control and maintenance at a particular building, the method comprising using a computer server having a processor to: (a) actuate a login module to provide selective access to users via one or more client computers communicably coupled to the server, the users including (i) occupants of the building having first level permissions and (ii) managers having second level permissions, wherein said selective access is granted based on said permissions; (b) enable users after having gained access to the server, to actuate a report access module to generate a report interface displayable on the client computers to enable the users to generate one or more building reports in the form of (i) thermal reports using a thermal report module, and/or (ii) maintenance reports using a maintenance report module; (c) actuate a geo-location module to assign a location within the building to each building report based on a floor plan of the building; (d) actuate an aggregation module to receive the building reports from the client computers, and to store and aggregate the building reports at the server along with additional information related to the building reports obtained from the floor plan; (e) actuate a View/Sort module to sort the aggregated reports according to their assigned locations, and to transmit the sorted reports to the one or more client computers for display; (f) actuate a rule storage module to store a set of comfort rules for the building; (g) actuate a Response/Notification module to (i) permit a manager at a client computer to access the server to view building reports and additional information stored by the aggregation module and to select for response, and assign a response status to, particular reports, and/or (ii) automatically respond and assign a response status to particular reports in accordance with said set of comfort rules; (h) actuate a checklist storage module to store a list of preventative maintenance items for the building; (i) actuate an inspection module to generate and populate a checklist interface on the user device, the checklist interface configured to display the list of preventative maintenance tasks, each of the tasks being user-selectable to designate completion of each individual task; and (j) actuate the aggregation module to store the status of the reports.
 14. The method of claim 13, comprising actuating the report access module to permit a client computer to generate a building report by scanning a QR code disposed at a predetermined location within the building.
 15. The method of claim 13, comprising actuating the report access module to permit a client computer to generate a building report by looking up a particular location within the building.
 16. The method of claim 13, comprising actuating the report access module to permit a client computer to apply a thermal comfort rating to one or more of the thermal reports.
 17. The method of claim 13, comprising actuating the report access module to permit a client computer to apply a maintenance request to one or more maintenance reports.
 18. The method of claim 13, comprising actuating a time-stamp module to store a time stamp denoting the time of creation and/or storage at the server, of each building report.
 19. The method of claim 13, comprising actuating a Comment/Customize module to permit a user at a client computer to add custom text and/or images to a report.
 20. The method of claim 19, comprising actuating the Comment/Customize module to permit the user to comment on reports. 